Document OAuth organization hints - #3159
Conversation
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a06015-04b9-70ab-aaba-bc0e8736680f Co-authored-by: Samuel Cochran <sj26@sj26.com>
![buildsworth-bk-app[bot]](https://avatars.githubusercontent.com/in/3010600?s=60&v=4){kind=small}
There was a problem hiding this comment.
The OAuth hints align with the linked server and CLI implementations. I left one non-blocking comment about where the new MCP guidance sits in the page hierarchy.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 24126, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
About buildsworth
Model: gpt-5.6-sol with xhigh thinking.
How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.
Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):
- L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
- L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
- L3 — High risk (auth, migrations, payments, secrets, perf-critical pipeline paths). Human review always required.
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-01a06015-04b9-70ab-aaba-bc0e8736680f Co-authored-by: Samuel Cochran <sj26@sj26.com>
Amp-Thread-ID: https://ampcode.com/threads/T-01a06015-04b9-70ab-aaba-bc0e8736680f Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: Samuel Cochran <sj26@sj26.com>
|
Is copied to and superseded by https://github.com/buildkite/docs-private/pull/2198 |
Pull request was closed
4 participants
Summary
Document how clients can preselect an organization during OAuth authorization:
organizationandorganization_uuidto the device authorization API reference.bk auth login --device --org my-orgfor CLI device login.Related implementation: